-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 2275456:[release-4.16] bundle: remove rook as a dependency to allow upgrades from 4.15 to 4.16 #400
Bug 2275456:[release-4.16] bundle: remove rook as a dependency to allow upgrades from 4.15 to 4.16 #400
Conversation
In older clusters, upgrading the odf channel from 4.15 to 4.16 tries to bring the rook-operator, leading to conflicts with ocs-operator 4.15, which already contains all Rook components in its 4.15 CSV. This conflict results in upgrade failures. To address this issue, the Rook dependency is removed from the odf-operator and added to the ocs-operator. This solution ensures a smooth upgrade process, as changing the ocs-operator channel will now bring Rook along with ocs-operator 4.16 without encountering conflicts. This commit should be reverted in 4.17 as 4.16 will feature different CSVs. In 4.17, reintroducing Rook as a dependency in odf should facilitate smooth installations and upgrades. Signed-off-by: Nitin Goyal <[email protected]>
Signed-off-by: Nitin Goyal <[email protected]>
@iamniting: This pull request references Bugzilla bug 2275456, which is valid. No validations were run on this bugRequesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: vavuthu. Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@iamniting: This pull request references Bugzilla bug 2275456, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: vavuthu. Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test odf-operator-e2e-aws |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: iamniting, malayparida2000 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/override ci/prow/odf-operator-e2e-aws |
@iamniting: Overrode contexts on behalf of iamniting: ci/prow/odf-operator-e2e-aws In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
46a0302
into
red-hat-storage:release-4.16
@iamniting: All pull requests linked via external trackers have merged:
Bugzilla bug 2275456 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is an manual cherry-pick of #399